Hi,

Is there a way to detect corrupted\bad items in an Exchange 2007\2010 mailbox, may be using EWS or PowerShell + MAPI?

Often Mailbox Moves fails due to corrupted\bad items in mailbox, so we want to know in advance if a mailbox has any bad items. I have searched it many times, but could not find answer. I also have detailed look into:

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/728141fb-3a9f-4bb3-a202-d11060b11fb5

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/8d78e08b-4ef9-4b28-a322-98a9dbc436e5

but could not find any answer.

Thanks in anticipation.

The Exchange Mailbox API's are designed to access valid items not fix corrupted ones.

The only thing that any of the Mailbox API's would be useful for is fixing items based around some criteria. Eg you would need to investigate and determine why migration of particular items are failing. If you can find the reason behind a failure (eg Single property corruption) then you can potentially write something that scans for that issue and fixes items before the migration (for example issue created by Blackberry devices etc) .

The problem with this is the number of reasons that an Item may fail to migrate could be large and very time consuming to determine because you may need to work through item by item yourself to determine it.

Cheers
Glen

The Exchange Mailbox API's are designed to access valid items not fix corrupted ones.

The only thing that any of the Mailbox API's would be useful for is fixing items based around some criteria. Eg you would need to investigate and determine why migration of particular items are failing. If you can find the reason behind a failure (eg Single property corruption) then you can potentially write something that scans for that issue and fixes items before the migration (for example issue created by Blackberry devices etc) .

The problem with this is the number of reasons that an Item may fail to migrate could be large and very time consuming to determine because you may need to work through item by item yourself to determine it.

Cheers
Glen

Hi,

Thanks Glen for participating in this discussion.

It seems that its really tough to find any related piece of source code or script for this issue. I was trying to find the way how move-maiilboxrequest cmdlet identifies an item as corrupt, and it seems there is no easy way to do this. I think there must be some doc\article related to it. It would really help organizations to konw in advnace how many corrupt\bad items a mailbox has before attempting to migrate\move it.

May be someone can give me link of any doc\article over this issue.

Thanks and Regards,

There is nice article by Tony Redmond on "Corrupted Items and Mailbox Moves in Exchange 2010". Hope this will help you.

http://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/bad-item-conundrum-143495

http://www.windowsitpro.com/article/exchange-server-2010/corrupted-items-mailbox-moves-exchange-2010-142659

Thanks

Shareef

Utilize next solution exchange server fix

In this material http://www.fixcorruptedexchangemailbox.exchangefixtool.com there are a lot of solution for ms exchange databases